Add PLEP 5 on versioning and releases #8
Conversation
|
@Cadair - Since I'm basing much of this PLEP on sunpy/sunpy-SEP#30, would you like to be a co-author? Alternatively, would you be willing to release sunpy/sunpy-SEP#30 under CC BY 4.0? |
|
@namurphy I am happy to be co-author. I also got around to merging the licence for the SEP repo: https://github.com/sunpy/sunpy-SEP/blob/master/LICENSE.md |
namurphy
changed the title
|
👍 |
|
Are there any more changes to come to this, @namurphy? If not I'll merge it :D |
|
Just to let you know, there has been a lot of discussion on sunpy/sunpy-SEP#30 about this, to the point where we are now probably going to take a slightly different approach. I would recommend you have a read over it all and consider how the arguments made there affect you. |
I added a draft decision rationale too.
|
Coordinating Committee members - please vote on PLEP 5! Any additional suggestions from the community are still appreciated. I vote in favor. 🙂 👍 (Also, during today's telecon we noted the discussion at sunpy/sunpy-SEP#30 with potential problems with using semantic versioning. If problems with semantic versioning do arise later on, we can still amend this PLEP to change the versioning scheme.) |
|
In favor! 👍 |
|
@StanczakDominik and @SolarDrew - Would either of you have a chance to vote on this soon? |
|
Oh, I thought I had done that, sorry. I vote yup.
|
|
👍 |
The purpose of this PlasmaPy Enrichment Proposal is to specify the versioning scheme to be used for PlasmaPy (for during development, prior to releases, and final releases), and the schedule for releases (no less frequently than once every six months).